Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix message monitor #104

Merged
merged 3 commits into from
Apr 2, 2024
Merged

fix message monitor #104

merged 3 commits into from
Apr 2, 2024

Conversation

kx1t
Copy link
Member

@kx1t kx1t commented Mar 25, 2024

No description provided.

@kx1t kx1t requested a review from fredclausen March 25, 2024 17:52
kx1t referenced this pull request Mar 25, 2024
…f we're within the adjustment timeframe (#92)

Co-authored-by: kx1t <[email protected]>
Copy link
Member

@fredclausen fredclausen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. My comment above is more about a general direction of the container and something we could address later, if need be.

@@ -278,7 +278,7 @@ You should now be feeding ADSB-ES & UAT to the "new" aggregators, FlightAware, a
| `LAT` | Latitude of your receiver. Only required if you want range statistics for InfluxDB, Prometheus, or tar1090/ultrafeeder graphs. | Unset |
| `LON` | Longitude of your receiver. Only required if you want range statistics for InfluxDB, Prometheus, or tar1090/ultrafeeder graphs. | Unset |
| `DUMP978_MSG_MONITOR_INTERVAL` | Interval between runs of the Message Monitor that checks if new messages are received. Format of value is anything that is accepted by the Linux `sleep` command | Unset (30 minutes) |
| `DUMP978_MSG_MONITOR_RESTART_WHEN_STALE` | If set to `true`/`on`/`yes`/`1`, the receiver process is restarted when no messages are received during the monitoring interval | Unset (`false`) |
| `DUMP978_MSG_MONITOR_RESTART_WHEN_STALE` | If set to `true`/`on`/`yes`/`1`, the receiver process is restarted when no messages are received during the monitoring interval | `true` |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this change reflected in the Dockerfile? I suspect the default already is true, but I’m not sure.

Also, I’m not sure I’m a fan of making it the default behavior. It is going to cause a lot of log spam in this container, as well as any other container that also plugs in and grabs UAT data if it is restarting with some frequency. Basically, what I think I’m ultimately saying is that the odds there is an actual reception issue are really low, and restarting the decoder isn’t really beneficial. That said, if the feeling among everyone is this is the better way, then I’m fine with it.

@fredclausen fredclausen merged commit 5939713 into main Apr 2, 2024
11 checks passed
@fredclausen fredclausen deleted the kx1t-patch-1 branch April 2, 2024 06:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants